Known Issues

• During the second reboot of runtime images including FBWF, the following erroneous event log entry is generated: "The configuration file for the file-based write filter is missing. Filtering is disabled." Ignore this event log entry; FBWF is configured later and the FBWF configuration file fbwf.cfg is generated.
  
  
• If FBWF is included on an image and is enabled after running Sysprep, the following error message is displayed before the splash screen appears.
  
  "We apologize for the inconvenience, but Windows did not start sucessfully......”
  
  The workaround is to delete the file <default drive>\Windows\bootstat.dat after Sysprep completes setup, but before FBWF is enabled on the machine.
  
  

• To add a multilingual user interface (MUI) pack to the runtime, you must add the Windows XP SP2 OOB Resource DLL component to the configuration manually. Without this component, some features such as .NET Messenger do not work correctly.
  
  
• To add a new connection by using the New Connection Wizard, you must manually add the Dial-Up Networking Common Libraries to the configuration. The size of your image increases when you add this component.
  
  
• To use Internet Explorer 6 and 7 to render HTML pages that use data binding, you must manually add Microsoft Data Access Components (MDAC) to the configuration. Without these components, the data binding feature do not display correctly. The size of your image increases when you add this component.
  
  
• To view the Windows splash screen or to listen to the title.wma file when using the First User Experience mode of Sysprep, you must manually add the Windows Media Player or Windows Media Player 6.4 components to the runtime.
  
  
• To use Group Policy with a WMI filter, you must manually add the WMI Win32 Provider component to the configuration.
  
  
• To use the Regular Black mouse cursor option in the Accessibility Wizard, you must manually add the Mouse Cursors component to the run time image. To add this component, in Target Designer, right-click the Mouse Cursors component located at \Software\System\User Interface\Shells\Windows Shell\, and then choose Add.
  
  
• To use the Regular Black mouse cursor option in the Accessibility Wizard, you need to modify the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cursors\Schemes\Windows Black. Add a space at the end of the value to modify it to "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Cursors\Schemes\Windows Black ".
  
  

If the runtime image includes both Registry Filter and Enhanced Write Filter (EWF) operating in RAM Reg mode, then you must start the system volume with EWF disabled, by doing the following.

• In Target Designer, in the EWF Configuration Settings dialog box, clear Start EWF Enabled for the system volume.
  
  

To ensure that the registry filter is initialized before EWF protects the volume, after the first boot agent completes, enable EWF manually

If you use Windows XP Embedded SP3 Tools deployed from Windows XP Professional or Windows Server 2003, you can prepare removable USB Flash Disks (UFD) for booting by using the UFDPREP.EXE tool.

UFDPREP.EXE is not supported on Windows Vista. To work around this issue, use the disk management API in Windows Vista to prepare UFDs and Compact Flash. The following procedure shows how to prepare a UFD using DISKPART and BOOTSECT utilities on Windows Vista.

When you add both the Chinese Traditional Language Support and the Chinese Simplified Language Support components to a configuration in Target Designer, the Regional and Language Settings component gets added as a dependency. When you configure the Regional and Language Options, the resulting image will always have Chinese Traditional as the user-interface language regardless of what you set in the User interface language dropdown box. In addition, the Language for non-Unicode program does not get repopulated correctly when you change the “User interface language” between Chinese Traditional and Chinese Simplified.

To work around this issue, add the International Control Panel component when building the image. After the first boot, you can manually change the language settings using the Regional and Language Options control panel.

Include the USB Boot Mass Storage Device component in your design only if the image is intended to boot from a USB storage device. Do not include the component if booting from a non-USB device such as IDE or SATA.

If you include the USB Boot Mass Storage Device component in a runtime configuration, the media type of the first enumerated USB-based storage device instance used with that embedded device will be marked as fixed type instead of removable because it is expected to serve as the Boot device. If instead of booting from a USB storage device, the image is incorrectly booted from a non-USB storage device such as IDE or SATA, the first enumerated USB-based storage device will appear as a fixed-type storage device. This causes the operating system to fail to offer Safely Remove Hardware in the System Tray for the first enumerated USB storage device. It also changes the data caching behavior of the storage device, which can cause data corruption and failure to disassociate its drive letter when it is unplugged. Fixed-type devices are intended to never be unplugged.

Regardless of whether you use the USB Boot Mass Storage Device, always use the Safely Remove Hardware tray icon to stop peripheral USB devices prior to removing them.

If you boot with a USB device, such as a USB scanner, connected to an embedded device with the USB Boot Mass Storage Device component as part of the embedded runtime, you may encounter a system hang during boot. If this occurs, boot from your USB storage device without other USB devices connected, then attach any additional USB devices to your embedded system.

The GUI dialog for Services may not have the Dependencies tab in your runtime image. To include this tab in the dialog box, you must include the Administration Support Tools component (required for displaying the list of Services) and the WMI Management Snap-ins (required for displaying Dependencies tab).

Software Update Services is now referred to as Windows Server Update Services (WSUS).

SDI Manager (located in \Program Files\Windows Embedded\utilities\SDIMgr.wsf) fails (cannot create SDIAUT.SDI object) on 64-bit Windows operating systems.

To workaround this issue, open a command prompt with administrator privileges and execute the following commands:

>cd %windir%\syswow64
>cmd.exe
>cscript //H:cscript //S
>sdimgr /new image.sdi

After uninstalling Windows XP Embedded SP3, files that were either in use during uninstall or were not installed by Windows XP Embedded SP3 will remain in the folder Program Files\Windows Embedded. These files have to be deleted manually if you wish to remove them from the system.

The batch file msdtcvtr.bat, located in %windir%\system32\msdtc\trace, is run with administrator privileges. Its ACL, which is inherited from its containing directory, allows write access to NT Authority\Network Service ACE which could pose a potential security risk. To mitigate this risk, remove the NetworkService ACE from this ACL prior to deploying your embedded images.

To use the Philips WDM TVTuner component, you must copy file "PSISLOAD.DLL from the repository {484C9D34-846E-40E2-A2E6-FF2771A303D5} and place it in folder %Windir%\System32. Alternatively, you can use the "Extra Files" node at the top in Target Designer.

Windows XP Embedded SP3 does not include functionality to re-start a custom shell that was closed inadvertently or unintentionally. Developers of custom shells may choose to develop a customized solution that provides this functionality.

The Group Policy Refresh Utility refreshes Group Policies settings.

The Group Policy Refresh Utility component contains no configurable options within Target Designer to specify a timeout value for the utility. The default value is 7 seconds.

To specify a different value:

1. Open the registry of the runtime image with Registry Editor or another registry editing tool.
   
   
2. Set the value of HKLM\Software\Policies\Microsoft\Windows\System GroupPolicyRefreshTime: DWORD to the desired value.
   
   Allowed values are limited to the range 7 – 3888000, (7 seconds to 45 days).
   
   

If Internet Explorer 7 is installed in the component database, then Outlook Express localization will fail.

The workaround for this issue is to copy the Outlook Express resource file "MSOERES.DLL.MUI" from the path <default drive>\Windows\mui\Fallback\<LCID>\MSOERES.DLL.MUI to path <default drive>\Program Files\Internet Explorer\MUI\<LCID>\MSOERES.DLL. The ".mui" extension should be removed from the resource file extensions after copying it to the destination directory.

The MUI components for RDP 6.1, shown as "<Language> Terminal Server Client MUI" must show in Target Designer with revision 5750 when building a configuration using MUI and RDP 6.1. If you require RDP 6.1 with MUI localization, ensure that you have installed the Windows XP Embedded SP3 MUI packs, and Target Designer shows the component version as 5750 prior to building your configuration. Not doing so may result in RDP 6.0 MUI files on the resulting runtime.

If you added the .Net 3.0 Framework Setup component with the Install .NET Framework 3.0 XP-Pro Install Package during FBA setting cleared, and built your runtime, you will not be able to open a XPS document on the runtime.

The following steps describe the workaround:

When your runtime has gone through FBA and you want to install after its boot

1. Check if the default value of the key HKCR\.xps has any value, if yes delete the value.
   
   
2. Install \windows\dotnetfx3.exe.
   
   

In Czech localization, there is an issue with Cscript font. The command window uses Terminal font to display text. Terminal font is based on code page 437 for English. So some Czech characters are not displayed correctly.

The work around is to add "Fonts: Fonts lucida_console" and "Command Window Property Page" component when building an image. In cmd.exe, use property sheet to switch font to Lucida console font. The text then displays correctly.

Windows XP Embedded SP3 ships with Adobe Flash Player 6.0. For the latest Adobe Flash Player software, visit this Web site.

There are 2 new public methods in the File Based Write Filter (FBWF) API that are not documented in the Windows XP Embedded SP3 help files. These methods are FbwfInitializeNotifications and FbwfUninitializeNotifications.

When using the FBWF API FbwfCacheThresholdNotification, call FbwfInitializeNotifications and FbwfUninitializeNotifications to start and stop respectively the worker thread required for sending cache threshold notifications.

If you applied security updates to a Windows XP Embedded SP3 installation with Internet Explorer 6, the updates get lost when you upgrade to Internet Explorer 7. You need to reapply the security updates to the component database after the upgrade.

By design, the context-sensitive help in Target Designer for Internet Explorer 6 and Internet Explorer 7 components is the same, and it is applicable for Internet Explorer 7. All the Internet Explorer 7 settings except Fishing Filter Option are applicable for Internet Explorer 6 as well. The setting Online Support URL, applicable to both Internet Explorer 6 and 7, was inadvertently missed in the Settings table in the help topic.

Similarly, the context-sensitive help for Windows Media Player 10 and Windows Media Player 11 components is the same.

• Certain topics titles in help files are not updated
  
  
• File resources for certain components require updates
  
  
• Registry key section of help topic for component Credential Roaming requires updates
  
  
• Certain topics require content updates